Issue with DirectoryIndex

I am having an issue with the DirectoryIndex. We have it set as
DirectoryIndex index.html We have a site the runs at https://www.site.com.
When we hit that site as shown it comes up fine because there is an
index.html file there. However, if we go further down to
http://www.site.com/tpg or http://www.site.com/tpg/docfiles/online either
with or without the ending /, we get a 404 error. I have tried moving the
DirectoryIndex to different areas of the conf file but cannot get it to
work. I know this is probably very basic, but I just cannot figure it out.
Thanks for any assistance.

John
--
View this message in context: http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5792416.html
Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com.


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Issue with DirectoryIndex

--000e0cd598da9ff6840475766d75
Content-Type: text/plain; charset=ISO-8859-1

404 means "file not found" which means you don't have any index.html file in
the other folders you try to access.

On Thu, Oct 8, 2009 at 5:58 AM, jwberger wrote:

>
> I am having an issue with the DirectoryIndex. We have it set as
> DirectoryIndex index.html We have a site the runs at https://www.site.com
> .
> When we hit that site as shown it comes up fine because there is an
> index.html file there. However, if we go further down to
> http://www.site.com/tpg or http://www.site.com/tpg/docfiles/online either
> with or without the ending /, we get a 404 error. I have tried moving the
> DirectoryIndex to different areas of the conf file but cannot get it to
> work. I know this is probably very basic, but I just cannot figure it out.
> Thanks for any assistance.
>
> John
> --
> View this message in context:
> http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5792416.html
> Sent from the Apache HTTP Server - Users mailing list archive at
> Nabble.com.
>
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>

--000e0cd598da9ff6840475766d75
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

404 means "file not found" which means you don't have any ind=
ex.html file in the other folders you try to access.

Re: Issue with DirectoryIndex

Igor Cicimov wrote:

> 404 means "file not found" which means you don't have any index.html
> file in the other folders you try to access.

I think if this were the case they would get 403, or if Options Indexes is
enabled, the listing of the files in the directory.

>
> On Thu, Oct 8, 2009 at 5:58 AM, jwberger > > wrote:
>
>
> I am having an issue with the DirectoryIndex. We have it set as
> DirectoryIndex index.html We have a site the runs at
> https://www.site.com.
> When we hit that site as shown it comes up fine because there is an
> index.html file there. However, if we go further down to
> http://www.site.com/tpg or http://www.site.com/tpg/docfiles/online
> either
> with or without the ending /, we get a 404 error. I have tried
> moving the
> DirectoryIndex to different areas of the conf file but cannot get it to
> work. I know this is probably very basic, but I just cannot figure
> it out.

Check the error log :)

--
Toomas Aas

.... Top Secret! Burn before reading!

------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Issue with DirectoryIndex

But there is an index.html file in that directory. If I go to
/tpg/docfiles/online/index.html it works just fine. It is only when we try
to just hit a directory. It happens on any subdirectory after the root.
Hitting the root without a filename works fine. It finds the index.html and
load up. None of the subdirectories work.

John


Igor Cicimov wrote:
>
> 404 means "file not found" which means you don't have any index.html file
> in
> the other folders you try to access.
>
> On Thu, Oct 8, 2009 at 5:58 AM, jwberger wrote:
>
>>
>> I am having an issue with the DirectoryIndex. We have it set as
>> DirectoryIndex index.html We have a site the runs at
>> https://www.site.com
>> .
>> When we hit that site as shown it comes up fine because there is an
>> index.html file there. However, if we go further down to
>> http://www.site.com/tpg or http://www.site.com/tpg/docfiles/online either
>> with or without the ending /, we get a 404 error. I have tried moving
>> the
>> DirectoryIndex to different areas of the conf file but cannot get it to
>> work. I know this is probably very basic, but I just cannot figure it
>> out.
>> Thanks for any assistance.
>>
>> John
>> --
>> View this message in context:
>> http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5792416.html
>> Sent from the Apache HTTP Server - Users mailing list archive at
>> Nabble.com.
>>
>>
>> ------------------------------------------------------------ ---------
>> The official User-To-User support forum of the Apache HTTP Server
>> Project.
>> See for more info.
>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>> " from the digest: users-digest-unsubscribe@httpd.apache.org
>> For additional commands, e-mail: users-help@httpd.apache.org
>>
>>
>
>

--
View this message in context: http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5820206.html
Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com.


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Issue with DirectoryIndex

Here is the some of the information from my conf file.


ServerAdmin admin@localhost
DocumentRoot "D:/docs"
ServerName x.x.x.x:8081
ServerAlias x.x.x.x:8081
ErrorLog "logs/partners3/error.log"
CustomLog "logs/partners3/access.log" common
SetEnvIf Remote_Addr "x\.x\.x\.x" dontlog
RewriteEngine On
RewriteCond %{REQUEST_METHOD} ^TRACE
ReWriteRule .* - [F]



ServerAdmin admin@localhost


ServerName x.x.x.x:8081

DocumentRoot "D:/docs"



Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all




Options Indexes FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all




DirectoryIndex index.html



John

Igor Cicimov wrote:
>
> 404 means "file not found" which means you don't have any index.html file
> in
> the other folders you try to access.
>
> On Thu, Oct 8, 2009 at 5:58 AM, jwberger wrote:
>
>>
>> I am having an issue with the DirectoryIndex. We have it set as
>> DirectoryIndex index.html We have a site the runs at
>> https://www.site.com
>> .
>> When we hit that site as shown it comes up fine because there is an
>> index.html file there. However, if we go further down to
>> http://www.site.com/tpg or http://www.site.com/tpg/docfiles/online either
>> with or without the ending /, we get a 404 error. I have tried moving
>> the
>> DirectoryIndex to different areas of the conf file but cannot get it to
>> work. I know this is probably very basic, but I just cannot figure it
>> out.
>> Thanks for any assistance.
>>
>> John
>> --
>> View this message in context:
>> http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5792416.html
>> Sent from the Apache HTTP Server - Users mailing list archive at
>> Nabble.com.
>>
>>
>> ------------------------------------------------------------ ---------
>> The official User-To-User support forum of the Apache HTTP Server
>> Project.
>> See for more info.
>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>> " from the digest: users-digest-unsubscribe@httpd.apache.org
>> For additional commands, e-mail: users-help@httpd.apache.org
>>
>>
>
>

--
View this message in context: http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5820306.html
Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com.


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Issue with DirectoryIndex

With the configuration structure show below, your DirectoryIndex
statement does not apply to the VirtualHost section. It applies to the
"main" configuration. When you use name-based VirtualHost sections,
whetever is outside of them normally only specifies defaults, overridden
(or not) by the directives in each VirtualHost section.
However, not all directives are automatically "inherited" by VirtualHost
sections. You should check if this one is.



jwberger wrote:

> Here is the some of the information from my conf file.
>
>
> ServerAdmin admin@localhost
> DocumentRoot "D:/docs"
> ServerName x.x.x.x:8081
> ServerAlias x.x.x.x:8081
> ErrorLog "logs/partners3/error.log"
> CustomLog "logs/partners3/access.log" common
> SetEnvIf Remote_Addr "x\.x\.x\.x" dontlog
> RewriteEngine On
> RewriteCond %{REQUEST_METHOD} ^TRACE
> ReWriteRule .* - [F]
>
>
>
> ServerAdmin admin@localhost
>
>
> ServerName x.x.x.x:8081
>
> DocumentRoot "D:/docs"
>
>
>
> Options FollowSymLinks
> AllowOverride None
> Order deny,allow
> Deny from all
>
>
>
>
> Options Indexes FollowSymLinks
> AllowOverride None
> Order allow,deny
> Allow from all
>
>
>
>
> DirectoryIndex index.html
>
>
>
> John
>
> Igor Cicimov wrote:
>> 404 means "file not found" which means you don't have any index.html file
>> in
>> the other folders you try to access.
>>
>> On Thu, Oct 8, 2009 at 5:58 AM, jwberger wrote:
>>
>>> I am having an issue with the DirectoryIndex. We have it set as
>>> DirectoryIndex index.html We have a site the runs at
>>> https://www.site.com
>>> .
>>> When we hit that site as shown it comes up fine because there is an
>>> index.html file there. However, if we go further down to
>>> http://www.site.com/tpg or http://www.site.com/tpg/docfiles/online either
>>> with or without the ending /, we get a 404 error. I have tried moving
>>> the
>>> DirectoryIndex to different areas of the conf file but cannot get it to
>>> work. I know this is probably very basic, but I just cannot figure it
>>> out.
>>> Thanks for any assistance.
>>>
>>> John
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5792416.html
>>> Sent from the Apache HTTP Server - Users mailing list archive at
>>> Nabble.com.
>>>
>>>
>>> ------------------------------------------------------------ ---------
>>> The official User-To-User support forum of the Apache HTTP Server
>>> Project.
>>> See for more info.
>>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>>> " from the digest: users-digest-unsubscribe@httpd.apache.org
>>> For additional commands, e-mail: users-help@httpd.apache.org
>>>
>>>
>>
>


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Issue with DirectoryIndex

How do I check to see if it is inheriting. Also, I tried adding the
DirectoryIndex in the VirtualHost section, but it still did not work.

John


awarnier wrote:
>
> With the configuration structure show below, your DirectoryIndex
> statement does not apply to the VirtualHost section. It applies to the
> "main" configuration. When you use name-based VirtualHost sections,
> whetever is outside of them normally only specifies defaults, overridden
> (or not) by the directives in each VirtualHost section.
> However, not all directives are automatically "inherited" by VirtualHost
> sections. You should check if this one is.
>
>
>
> jwberger wrote:
>
>> Here is the some of the information from my conf file.
>>
>>
>> ServerAdmin admin@localhost
>> DocumentRoot "D:/docs"
>> ServerName x.x.x.x:8081
>> ServerAlias x.x.x.x:8081
>> ErrorLog "logs/partners3/error.log"
>> CustomLog "logs/partners3/access.log" common
>> SetEnvIf Remote_Addr "x\.x\.x\.x" dontlog
>> RewriteEngine On
>> RewriteCond %{REQUEST_METHOD} ^TRACE
>> ReWriteRule .* - [F]
>>
>>
>>
>> ServerAdmin admin@localhost
>>
>>
>> ServerName x.x.x.x:8081
>>
>> DocumentRoot "D:/docs"
>>
>>
>>
>> Options FollowSymLinks
>> AllowOverride None
>> Order deny,allow
>> Deny from all
>>
>>
>>
>>
>> Options Indexes FollowSymLinks
>> AllowOverride None
>> Order allow,deny
>> Allow from all
>>
>>
>>
>>
>> DirectoryIndex index.html
>>
>>
>>
>> John
>>
>> Igor Cicimov wrote:
>>> 404 means "file not found" which means you don't have any index.html
>>> file
>>> in
>>> the other folders you try to access.
>>>
>>> On Thu, Oct 8, 2009 at 5:58 AM, jwberger wrote:
>>>
>>>> I am having an issue with the DirectoryIndex. We have it set as
>>>> DirectoryIndex index.html We have a site the runs at
>>>> https://www.site.com
>>>> .
>>>> When we hit that site as shown it comes up fine because there is an
>>>> index.html file there. However, if we go further down to
>>>> http://www.site.com/tpg or http://www.site.com/tpg/docfiles/online
>>>> either
>>>> with or without the ending /, we get a 404 error. I have tried moving
>>>> the
>>>> DirectoryIndex to different areas of the conf file but cannot get it to
>>>> work. I know this is probably very basic, but I just cannot figure it
>>>> out.
>>>> Thanks for any assistance.
>>>>
>>>> John
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5792416.html
>>>> Sent from the Apache HTTP Server - Users mailing list archive at
>>>> Nabble.com.
>>>>
>>>>
>>>> ------------------------------------------------------------ ---------
>>>> The official User-To-User support forum of the Apache HTTP Server
>>>> Project.
>>>> See for more info.
>>>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>>>> " from the digest: users-digest-unsubscribe@httpd.apache.org
>>>> For additional commands, e-mail: users-help@httpd.apache.org
>>>>
>>>>
>>>
>>
>
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
>

--
View this message in context: http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5821511.html
Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com.


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Issue with DirectoryIndex

What version of Apache are you using, on which platform ?
Can you give us you whole configuration file ? What you are telling us
about your configuration, and the URLs which you mentioned in your first
post, do not match.
About this :

Are you sure that you are really using name-based virtual hosts, or is
this an address-based virtual host scheme ?
In any case, the following lines are probably incorrect :
ServerName x.x.x.x:8081
ServerAlias x.x.x.x:8081
ServerAlias should not include a port number. ServerName can include
one, but only if you really know what you are doing.
What do your "Listen" and "NameVirtualHost" directives look like ?

The reason for all the questions and remarks above is : under Apache
2.x, there are hundreds or thousands of systems where the DirectoryIndex
works exactly as expected. So the problem in all likelihood is not with
Apache, but with something in your configuration which prevents it from
working. But the information you provide seems incomplete or
inaccurate, so it is difficult to help you.


jwberger wrote:
> How do I check to see if it is inheriting. Also, I tried adding the
> DirectoryIndex in the VirtualHost section, but it still did not work.
>
> John
>
>
> awarnier wrote:
>> With the configuration structure show below, your DirectoryIndex
>> statement does not apply to the VirtualHost section. It applies to the
>> "main" configuration. When you use name-based VirtualHost sections,
>> whetever is outside of them normally only specifies defaults, overridden
>> (or not) by the directives in each VirtualHost section.
>> However, not all directives are automatically "inherited" by VirtualHost
>> sections. You should check if this one is.
>>
>>
>>
>> jwberger wrote:
>>
>>> Here is the some of the information from my conf file.
>>>
>>>
>>> ServerAdmin admin@localhost
>>> DocumentRoot "D:/docs"
>>> ServerName x.x.x.x:8081
>>> ServerAlias x.x.x.x:8081
>>> ErrorLog "logs/partners3/error.log"
>>> CustomLog "logs/partners3/access.log" common
>>> SetEnvIf Remote_Addr "x\.x\.x\.x" dontlog
>>> RewriteEngine On
>>> RewriteCond %{REQUEST_METHOD} ^TRACE
>>> ReWriteRule .* - [F]
>>>
>>>
>>>
>>> ServerAdmin admin@localhost
>>>
>>>
>>> ServerName x.x.x.x:8081
>>>
>>> DocumentRoot "D:/docs"
>>>
>>>
>>>
>>> Options FollowSymLinks
>>> AllowOverride None
>>> Order deny,allow
>>> Deny from all
>>>
>>>
>>>
>>>
>>> Options Indexes FollowSymLinks
>>> AllowOverride None
>>> Order allow,deny
>>> Allow from all
>>>
>>>
>>>
>>>
>>> DirectoryIndex index.html
>>>
>>>
>>>
>>> John
>>>
>>> Igor Cicimov wrote:
>>>> 404 means "file not found" which means you don't have any index.html
>>>> file
>>>> in
>>>> the other folders you try to access.
>>>>
>>>> On Thu, Oct 8, 2009 at 5:58 AM, jwberger wrote:
>>>>
>>>>> I am having an issue with the DirectoryIndex. We have it set as
>>>>> DirectoryIndex index.html We have a site the runs at
>>>>> https://www.site.com
>>>>> .
>>>>> When we hit that site as shown it comes up fine because there is an
>>>>> index.html file there. However, if we go further down to
>>>>> http://www.site.com/tpg or http://www.site.com/tpg/docfiles/online
>>>>> either
>>>>> with or without the ending /, we get a 404 error. I have tried moving
>>>>> the
>>>>> DirectoryIndex to different areas of the conf file but cannot get it to
>>>>> work. I know this is probably very basic, but I just cannot figure it
>>>>> out.
>>>>> Thanks for any assistance.
>>>>>
>>>>> John
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5792416.html
>>>>> Sent from the Apache HTTP Server - Users mailing list archive at
>>>>> Nabble.com.
>>>>>
>>>>>
>>>>> ------------------------------------------------------------ ---------
>>>>> The official User-To-User support forum of the Apache HTTP Server
>>>>> Project.
>>>>> See for more info.
>>>>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>>>>> " from the digest: users-digest-unsubscribe@httpd.apache.org
>>>>> For additional commands, e-mail: users-help@httpd.apache.org
>>>>>
>>>>>
>>
>> ------------------------------------------------------------ ---------
>> The official User-To-User support forum of the Apache HTTP Server Project.
>> See for more info.
>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>> " from the digest: users-digest-unsubscribe@httpd.apache.org
>> For additional commands, e-mail: users-help@httpd.apache.org
>>
>>
>>
>


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Issue with DirectoryIndex

I completely agree that it is most likely an issue with my config. I am
pretty new to Apache. Below is the complete config. I know I probably did
not do some things correctly, but it is working good for except for this one
thing that has just come up.


ServerRoot "C:/Program Files/Apache Software Foundation/Apache2.2"


Listen 168.127.1.19:8081


LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_alias_module modules/mod_authn_alias.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
#LoadModule disk_cache_module modules/mod_disk_cache.so
#LoadModule dumpio_module modules/mod_dumpio.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule filter_module modules/mod_filter.so
#LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
LoadModule ldap_module modules/mod_ldap.so
#LoadModule logio_module modules/mod_logio.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule ssl_module modules/mod_ssl.so
#LoadModule status_module modules/mod_status.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule unique_id_module modules/mod_unique_id.so
#LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule version_module modules/mod_version.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule weblogic_module modules/mod_wl_22.so




User daemon
Group daemon





WebLogicCluster 168.127.136.85:9060
KeepAliveEnabled ON
KeepAliveSecs 30
FileCaching OFF



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060
FileCaching OFF



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060



SetHandler weblogic-handler
WebLogicCluster 168.127.133.168:9040,168.127.133.167:9040



SetHandler weblogic-handler
WebLogicCluster 168.127.133.168:9040,168.127.133.167:9040



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060



SetHandler weblogic-handler
WebLogicCluster 168.127.133.168:9040,168.127.133.167:9040



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060
Debug OFF
# WLLogFile c:/partner3-wl-proxy.log
DebugConfigInfo OFF
KeepAliveEnabled ON
KeepAliveSecs 30
FileCaching OFF



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060



SetHandler weblogic-handler
WebLogicCluster 168.127.136.85:9060



SetHandler weblogic-handler
WebLogicCluster 168.127.133.168:9040,168.127.133.167:9040



SetHandler weblogic-handler
WebLogicCluster 168.127.133.168:9040,168.127.133.167:9040



SetHandler weblogic-handler
WebLogicCluster 168.127.133.168:9040,168.127.133.167:9040



SetHandler weblogic-handler
WebLogicCluster 168.127.133.168:9040,168.127.133.167:9040



SetHandler weblogic-handler
WebLogicCluster 168.127.133.168:9040,168.127.133.167:9040



AuthType basic
AuthBasicProvider ldap
AuthName "Partners"
SetHandler test
Order deny,allow
Deny from all
Allow from all
# AuthLDAPURL ldap://boris.fnc.net.local:389/o=directory1.fnc.fujitsu.com
AuthLDAPURL
ldap://rchdmzldapd1.fnc.fujitsu.com:389/o=directory1.fnc.fuj itsu.com
AuthzLDAPAuthoritative off
Require valid-user



AuthType basic
AuthBasicProvider ldap
AuthName "Partners"
SetHandler test
Order deny,allow
Deny from all
Allow from all
# AuthLDAPURL ldap://boris.fnc.net.local:389/o=directory1.fnc.fujitsu.com
AuthLDAPURL
ldap://rchdmzldapd1.fnc.fujitsu.com:389/o=directory1.fnc.fuj itsu.com
AuthzLDAPAuthoritative off
Require valid-user



AuthType basic
AuthBasicProvider ldap
AuthName "Partners"
SetHandler test
Order deny,allow
Deny from all
Allow from all
# AuthLDAPURL ldap://boris.fnc.net.local:389/o=directory1.fnc.fujitsu.com
AuthLDAPURL
ldap://rchdmzldapd1.fnc.fujitsu.com:389/o=directory1.fnc.fuj itsu.com
AuthzLDAPAuthoritative off
Require valid-user





ServerAdmin admin@localhost
DocumentRoot "D:/docs"
ServerName 168.127.1.19:8081
ServerAlias 168.127.1.19:8081
# UseCanonicalName off
ErrorLog "logs/partners3/error.log"
CustomLog "logs/partners3/access.log" common
SetEnvIf Remote_Addr "168\.127\.1\.59" dontlog
RewriteEngine On
RewriteOptions Inherit
RewriteCond %{REQUEST_METHOD} ^TRACE
ReWriteRule .* - [F]



ServerAdmin admin@localhost


ServerName 168.127.1.19:8081


DocumentRoot "D:/docs"



Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all





Options Indexes FollowSymLinks


AllowOverride None


Order allow,deny
Allow from all





DirectoryIndex index.html




Order allow,deny
Deny from all
Satisfy All



LogLevel warn



LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\""
combined
LogFormat "%{clientip}i %h %l %u %t \"%r\" %>s %b" common


# You need to enable mod_logio.c to use %I and %O
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
\"%{User-Agent}i\" %I %O" combinedio



CustomLog "logs/access.log" common






ScriptAlias /cgi-bin/ "C:/Program Files/Apache Software
Foundation/Apache2.2/cgi-bin/"




#
# ScriptSock: On threaded servers, designate the path to the UNIX
# socket used to communicate with the CGI daemon of mod_cgid.
#
#Scriptsock logs/cgisock




AllowOverride None
Options None
Order allow,deny
Allow from all



DefaultType text/plain



TypesConfig conf/mime.types


AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz

#
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the
server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
#AddHandler cgi-script .cgi

# For type maps (negotiated resources):
#AddHandler type-map var

#
# Filters allow you to process content before it is sent to the client.
#
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml




SSLRandomSeed startup builtin
SSLRandomSeed connect builtin



John

awarnier wrote:
>
> What version of Apache are you using, on which platform ?
> Can you give us you whole configuration file ? What you are telling us
> about your configuration, and the URLs which you mentioned in your first
> post, do not match.
> About this :
>
> Are you sure that you are really using name-based virtual hosts, or is
> this an address-based virtual host scheme ?
> In any case, the following lines are probably incorrect :
> ServerName x.x.x.x:8081
> ServerAlias x.x.x.x:8081
> ServerAlias should not include a port number. ServerName can include
> one, but only if you really know what you are doing.
> What do your "Listen" and "NameVirtualHost" directives look like ?
>
> The reason for all the questions and remarks above is : under Apache
> 2.x, there are hundreds or thousands of systems where the DirectoryIndex
> works exactly as expected. So the problem in all likelihood is not with
> Apache, but with something in your configuration which prevents it from
> working. But the information you provide seems incomplete or
> inaccurate, so it is difficult to help you.
>
>
> jwberger wrote:
>> How do I check to see if it is inheriting. Also, I tried adding the
>> DirectoryIndex in the VirtualHost section, but it still did not work.
>>
>> John
>>
>>
>> awarnier wrote:
>>> With the configuration structure show below, your DirectoryIndex
>>> statement does not apply to the VirtualHost section. It applies to the
>>> "main" configuration. When you use name-based VirtualHost sections,
>>> whetever is outside of them normally only specifies defaults, overridden
>>> (or not) by the directives in each VirtualHost section.
>>> However, not all directives are automatically "inherited" by VirtualHost
>>> sections. You should check if this one is.
>>>
>>>
>>>
>>> jwberger wrote:
>>>
>>>> Here is the some of the information from my conf file.
>>>>
>>>>
>>>> ServerAdmin admin@localhost
>>>> DocumentRoot "D:/docs"
>>>> ServerName x.x.x.x:8081
>>>> ServerAlias x.x.x.x:8081
>>>> ErrorLog "logs/partners3/error.log"
>>>> CustomLog "logs/partners3/access.log" common
>>>> SetEnvIf Remote_Addr "x\.x\.x\.x" dontlog
>>>> RewriteEngine On
>>>> RewriteCond %{REQUEST_METHOD} ^TRACE
>>>> ReWriteRule .* - [F]
>>>>
>>>>
>>>>
>>>> ServerAdmin admin@localhost
>>>>
>>>>
>>>> ServerName x.x.x.x:8081
>>>>
>>>> DocumentRoot "D:/docs"
>>>>
>>>>
>>>>
>>>> Options FollowSymLinks
>>>> AllowOverride None
>>>> Order deny,allow
>>>> Deny from all
>>>>
>>>>
>>>>
>>>>
>>>> Options Indexes FollowSymLinks
>>>> AllowOverride None
>>>> Order allow,deny
>>>> Allow from all
>>>>
>>>>
>>>>
>>>>
>>>> DirectoryIndex index.html
>>>>
>>>>
>>>>
>>>> John
>>>>
>>>> Igor Cicimov wrote:
>>>>> 404 means "file not found" which means you don't have any index.html
>>>>> file
>>>>> in
>>>>> the other folders you try to access.
>>>>>
>>>>> On Thu, Oct 8, 2009 at 5:58 AM, jwberger
>>>>> wrote:
>>>>>
>>>>>> I am having an issue with the DirectoryIndex. We have it set as
>>>>>> DirectoryIndex index.html We have a site the runs at
>>>>>> https://www.site.com
>>>>>> .
>>>>>> When we hit that site as shown it comes up fine because there is an
>>>>>> index.html file there. However, if we go further down to
>>>>>> http://www.site.com/tpg or http://www.site.com/tpg/docfiles/online
>>>>>> either
>>>>>> with or without the ending /, we get a 404 error. I have tried
>>>>>> moving
>>>>>> the
>>>>>> DirectoryIndex to different areas of the conf file but cannot get it
>>>>>> to
>>>>>> work. I know this is probably very basic, but I just cannot figure
>>>>>> it
>>>>>> out.
>>>>>> Thanks for any assistance.
>>>>>>
>>>>>> John
>>>>>> --
>>>>>> View this message in context:
>>>>>> http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5792416.html
>>>>>> Sent from the Apache HTTP Server - Users mailing list archive at
>>>>>> Nabble.com.
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------ ---------
>>>>>> The official User-To-User support forum of the Apache HTTP Server
>>>>>> Project.
>>>>>> See for more info.
>>>>>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>>>>>> " from the digest: users-digest-unsubscribe@httpd.apache.org
>>>>>> For additional commands, e-mail: users-help@httpd.apache.org
>>>>>>
>>>>>>
>>>
>>> ------------------------------------------------------------ ---------
>>> The official User-To-User support forum of the Apache HTTP Server
>>> Project.
>>> See for more info.
>>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>>> " from the digest: users-digest-unsubscribe@httpd.apache.org
>>> For additional commands, e-mail: users-help@httpd.apache.org
>>>
>>>
>>>
>>
>
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
>

--
View this message in context: http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5822187.html
Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com.


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Issue with DirectoryIndex

Forgot to mention we are running 2.2.9 on Windows 2003. We are also behind a
load balance switch. So, technically users come in https and the lb switch
drops it down to the server running http port 8081.

John


awarnier wrote:
>
> What version of Apache are you using, on which platform ?
> Can you give us you whole configuration file ? What you are telling us
> about your configuration, and the URLs which you mentioned in your first
> post, do not match.
> About this :
>
> Are you sure that you are really using name-based virtual hosts, or is
> this an address-based virtual host scheme ?
> In any case, the following lines are probably incorrect :
> ServerName x.x.x.x:8081
> ServerAlias x.x.x.x:8081
> ServerAlias should not include a port number. ServerName can include
> one, but only if you really know what you are doing.
> What do your "Listen" and "NameVirtualHost" directives look like ?
>
> The reason for all the questions and remarks above is : under Apache
> 2.x, there are hundreds or thousands of systems where the DirectoryIndex
> works exactly as expected. So the problem in all likelihood is not with
> Apache, but with something in your configuration which prevents it from
> working. But the information you provide seems incomplete or
> inaccurate, so it is difficult to help you.
>
>
> jwberger wrote:
>> How do I check to see if it is inheriting. Also, I tried adding the
>> DirectoryIndex in the VirtualHost section, but it still did not work.
>>
>> John
>>
>>
>> awarnier wrote:
>>> With the configuration structure show below, your DirectoryIndex
>>> statement does not apply to the VirtualHost section. It applies to the
>>> "main" configuration. When you use name-based VirtualHost sections,
>>> whetever is outside of them normally only specifies defaults, overridden
>>> (or not) by the directives in each VirtualHost section.
>>> However, not all directives are automatically "inherited" by VirtualHost
>>> sections. You should check if this one is.
>>>
>>>
>>>
>>> jwberger wrote:
>>>
>>>> Here is the some of the information from my conf file.
>>>>
>>>>
>>>> ServerAdmin admin@localhost
>>>> DocumentRoot "D:/docs"
>>>> ServerName x.x.x.x:8081
>>>> ServerAlias x.x.x.x:8081
>>>> ErrorLog "logs/partners3/error.log"
>>>> CustomLog "logs/partners3/access.log" common
>>>> SetEnvIf Remote_Addr "x\.x\.x\.x" dontlog
>>>> RewriteEngine On
>>>> RewriteCond %{REQUEST_METHOD} ^TRACE
>>>> ReWriteRule .* - [F]
>>>>
>>>>
>>>>
>>>> ServerAdmin admin@localhost
>>>>
>>>>
>>>> ServerName x.x.x.x:8081
>>>>
>>>> DocumentRoot "D:/docs"
>>>>
>>>>
>>>>
>>>> Options FollowSymLinks
>>>> AllowOverride None
>>>> Order deny,allow
>>>> Deny from all
>>>>
>>>>
>>>>
>>>>
>>>> Options Indexes FollowSymLinks
>>>> AllowOverride None
>>>> Order allow,deny
>>>> Allow from all
>>>>
>>>>
>>>>
>>>>
>>>> DirectoryIndex index.html
>>>>
>>>>
>>>>
>>>> John
>>>>
>>>> Igor Cicimov wrote:
>>>>> 404 means "file not found" which means you don't have any index.html
>>>>> file
>>>>> in
>>>>> the other folders you try to access.
>>>>>
>>>>> On Thu, Oct 8, 2009 at 5:58 AM, jwberger
>>>>> wrote:
>>>>>
>>>>>> I am having an issue with the DirectoryIndex. We have it set as
>>>>>> DirectoryIndex index.html We have a site the runs at
>>>>>> https://www.site.com
>>>>>> .
>>>>>> When we hit that site as shown it comes up fine because there is an
>>>>>> index.html file there. However, if we go further down to
>>>>>> http://www.site.com/tpg or http://www.site.com/tpg/docfiles/online
>>>>>> either
>>>>>> with or without the ending /, we get a 404 error. I have tried
>>>>>> moving
>>>>>> the
>>>>>> DirectoryIndex to different areas of the conf file but cannot get it
>>>>>> to
>>>>>> work. I know this is probably very basic, but I just cannot figure
>>>>>> it
>>>>>> out.
>>>>>> Thanks for any assistance.
>>>>>>
>>>>>> John
>>>>>> --
>>>>>> View this message in context:
>>>>>> http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5792416.html
>>>>>> Sent from the Apache HTTP Server - Users mailing list archive at
>>>>>> Nabble.com.
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------ ---------
>>>>>> The official User-To-User support forum of the Apache HTTP Server
>>>>>> Project.
>>>>>> See for more info.
>>>>>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>>>>>> " from the digest: users-digest-unsubscribe@httpd.apache.org
>>>>>> For additional commands, e-mail: users-help@httpd.apache.org
>>>>>>
>>>>>>
>>>
>>> ------------------------------------------------------------ ---------
>>> The official User-To-User support forum of the Apache HTTP Server
>>> Project.
>>> See for more info.
>>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>>> " from the digest: users-digest-unsubscribe@httpd.apache.org
>>> For additional commands, e-mail: users-help@httpd.apache.org
>>>
>>>
>>>
>>
>
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
>

--
View this message in context: http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5822207.html
Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com.


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Issue with DirectoryIndex

jwberger wrote:
> I completely agree that it is most likely an issue with my config. I am
> pretty new to Apache. Below is the complete config. I know I probably did
> not do some things correctly, but it is working good for except for this one
> thing that has just come up.

No problem. This forum is the right place for that.
As the final response will show, it just helps people here (for helping
you) if you provide the full information from the start. Just 2 lines with
Apache version : x.y.z
platform : x.y v 0.3
already narrow down the issue quite a bit.
(And in this case, it would have helped a lot to mention that you are
using Apache as a proxy to a WebLogic cluster; but let's not get ahead
of ourselves).

I am going to give you some personal comments below, which you might
decide to use or not. Just based on personal experience.

>
>
> ServerRoot "C:/Program Files/Apache Software Foundation/Apache2.2"
>
This is the standard installation path for the Apache/Windows MSI installer.
It is OK, but I dislike it, because the path contains spaces, and spaces
in paths will always bite you somewhere down the line.
(E.g. when you call a script with another script and forget to quote
things properly).

In my opinion, the person who invented paths with spaces in them should
get an Ig Nobel prize.

>
> Listen 168.127.1.19:8081
>
This could probably just be
Listen 8081

As you put it above it is valid, but it means that this Apache server
will listen *only* on requests that come in on the interface that has
that specific IP address. For example, it would not listen for requests
on the "loopback" interface (127.0.0.1), and it would not listen anymore
if ever you changed the IP address of the server.

>
> LoadModule actions_module modules/mod_actions.so
....
OK
....
>
>
> WebLogicCluster 168.127.136.85:9060
> KeepAliveEnabled ON
> KeepAliveSecs 30
> FileCaching OFF
>
>
>
> SetHandler weblogic-handler
> WebLogicCluster 168.127.136.85:9060
>
>
The above and similar sections are not standard Apache stuff, and
belongs to your WebLogic add-ons.
This is intriguing. Where from did you get this Apache ?

>

AuthType basic
AuthBasicProvider ldap
AuthName "Partners"
SetHandler test
Order deny,allow
Deny from all
Allow from all
# AuthLDAPURL ldap://boris.fnc.net.local:389/o=directory1.fnc.fujitsu.com
AuthLDAPURL
ldap://rchdmzldapd1.fnc.fujitsu.com:389/o=directory1.fnc.fuj itsu.com
AuthzLDAPAuthoritative off
Require valid-user
>

Ok, so far we are in what is called the "main configuration", meaning
outside of any VirtualHost section.
If you are using VirtualHost sections, then all this stuff in fact
describes default values, that will be used by each VirtualHost later
defined, unless that VirtualHost re-defines that particular parameter
itself.

Next, I have taken out your section, because where it was
located in your configuration file, it was a bit confusing.

All the following directives, being also outside of the
section, are in fact member of the same group as the ones above. They
belong to the main configuration, and also act as defaults for all
VirtualHosts.

>
>
> ServerAdmin admin@localhost
> ServerName 168.127.1.19:8081
This is, again, just a default value. It is in fact never used in this
case.

>
> DocumentRoot "D:/docs"
>
> Options FollowSymLinks
> AllowOverride None
> Order deny,allow
> Deny from all
>
Nitpick: the "Options FollowSymlinks" above does not seem to be useful,
since you are forbidding access to "/" anyway (and rightly so).

>
> Options Indexes FollowSymLinks
> AllowOverride None
> Order allow,deny
> Allow from all
>
>
> DirectoryIndex index.html
>
>
So it would seem that indeed you set the DirectoryIndex directive in the
main configuration, and that it should thus be inherited by all
VirtualHosts. Then why is it not working ? Mmmm.

....
>
I moved the section here at the end, because it seems more
logical to first have all the default directives applying to all
VirtualHosts, and then the definition of these VirtualHosts.

>
>

So this is not a name-based VirtualHost system, it is an IP-based
VirtualHost system, which is quite a different animal.

> ServerAdmin admin@localhost
> DocumentRoot "D:/docs"
> ServerName 168.127.1.19:8081
> ServerAlias 168.127.1.19:8081
> # UseCanonicalName off
> ErrorLog "logs/partners3/error.log"
> CustomLog "logs/partners3/access.log" common
> SetEnvIf Remote_Addr "168\.127\.1\.59" dontlog
> RewriteEngine On
> RewriteOptions Inherit
> RewriteCond %{REQUEST_METHOD} ^TRACE
> ReWriteRule .* - [F]
>
>

The VirtualHost section does not redefine DirectoryIndex. The mystery
gets thicker..

But let's get back to your section


In that section, you have a line
SetHandler test
(just like in other sections, you have a line
SetHandler weblogic-handler

Now THAT is the reason why your DirectoryIndex is not working !
By this SetHandler directive, you are in fact telling Apache not to
generate the content by itself, but to "delegate" (or proxy) this call
to some add-on module. So Apache gives this request (any request for
any URL starting with /tpg) to the "test" or to the "weblogic-handler"
module, and expects this module to generate the response. And,
presumably, these handlers have no idea that they should look for an
"index.html" file in some directory.
So they return whatever response they would return when give a URL of
"/tpg" (probably, an error), and then Apache returns that response to
the browser.

It is only when Apache is asked to generate the content itself, with its
own "default handler", that the DirectoryIndex directive will be
invoked. In your case, Apache is not looking for anything, on disk or
elsewhere. It is just passing the request to the module that you
indicated as the handler.

Do the following test :
Add a new section as follows :


SetHandler none
DirectoryIndex index.html


then make sure that you have a directory C:/Docs/tpg/indextest, and that
it contains an "index.html" file.
Then request http://hostname/tpg/indextest and see what happens.


Because this is a sub-location of /tpg, and /tpg is defined to use the
"test" handler (supposing it exists), we have to override this if we
want Apache to use its normal own code to provide the response for a URL
of /tpg/something.
From there the "SetHandler none".
See : http://httpd.apache.org/docs/2.2/mod/core.html#sethandler

Also, it would have been impossible for anyone to find this out, if they
did not see the full configuration above.

------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Issue with DirectoryIndex

I apologize for my lack of understanding. Next time I will give version and
platform along with the full configuration in the future. To answer you
question about the Weblogic stuff. The mod_wl_22.so file came from my
Weblogic installation. It is there proxy file. Also the Location
information for Weblogic came from them too.

The only reason I have the IP address and port list is that I am running two
different sites on this box. They are both running on the same IP but on
different ports. I have each site running as a Windows service so I can
easily stop and restart the site.

I agree with you on the space in folders. I do not like them either, but I
just went with the defaults.

Adding the new Location with the SetHandler to none worked. Not really sure
where I got the test. Most likely I misunderstood some information I read.
So, if I set the three locations /tpg, /Softwaredownloads and /focis to none
on the SetHandlers, do you think that might fix it?

John



awarnier wrote:
>
> jwberger wrote:
>> I completely agree that it is most likely an issue with my config. I am
>> pretty new to Apache. Below is the complete config. I know I probably
>> did
>> not do some things correctly, but it is working good for except for this
>> one
>> thing that has just come up.
>
> No problem. This forum is the right place for that.
> As the final response will show, it just helps people here (for helping
> you) if you provide the full information from the start. Just 2 lines with
> Apache version : x.y.z
> platform : x.y v 0.3
> already narrow down the issue quite a bit.
> (And in this case, it would have helped a lot to mention that you are
> using Apache as a proxy to a WebLogic cluster; but let's not get ahead
> of ourselves).
>
> I am going to give you some personal comments below, which you might
> decide to use or not. Just based on personal experience.
>
>>
>>
>> ServerRoot "C:/Program Files/Apache Software Foundation/Apache2.2"
>>
> This is the standard installation path for the Apache/Windows MSI
> installer.
> It is OK, but I dislike it, because the path contains spaces, and spaces
> in paths will always bite you somewhere down the line.
> (E.g. when you call a script with another script and forget to quote
> things properly).
>
> In my opinion, the person who invented paths with spaces in them should
> get an Ig Nobel prize.
>
>>
>> Listen 168.127.1.19:8081
>>
> This could probably just be
> Listen 8081
>
> As you put it above it is valid, but it means that this Apache server
> will listen *only* on requests that come in on the interface that has
> that specific IP address. For example, it would not listen for requests
> on the "loopback" interface (127.0.0.1), and it would not listen anymore
> if ever you changed the IP address of the server.
>
>>
>> LoadModule actions_module modules/mod_actions.so
> ...
> OK
> ...
>>
>>
>> WebLogicCluster 168.127.136.85:9060
>> KeepAliveEnabled ON
>> KeepAliveSecs 30
>> FileCaching OFF
>>
>>
>>
>> SetHandler weblogic-handler
>> WebLogicCluster 168.127.136.85:9060
>>
>>
> The above and similar sections are not standard Apache stuff, and
> belongs to your WebLogic add-ons.
> This is intriguing. Where from did you get this Apache ?
>
>>
>
> AuthType basic
> AuthBasicProvider ldap
> AuthName "Partners"
> SetHandler test
> Order deny,allow
> Deny from all
> Allow from all
> # AuthLDAPURL ldap://boris.fnc.net.local:389/o=directory1.fnc.fujitsu.com
> AuthLDAPURL
> ldap://rchdmzldapd1.fnc.fujitsu.com:389/o=directory1.fnc.fuj itsu.com
> AuthzLDAPAuthoritative off
> Require valid-user
> >
>
> Ok, so far we are in what is called the "main configuration", meaning
> outside of any VirtualHost section.
> If you are using VirtualHost sections, then all this stuff in fact
> describes default values, that will be used by each VirtualHost later
> defined, unless that VirtualHost re-defines that particular parameter
> itself.
>
> Next, I have taken out your section, because where it was
> located in your configuration file, it was a bit confusing.
>
> All the following directives, being also outside of the
> section, are in fact member of the same group as the ones above. They
> belong to the main configuration, and also act as defaults for all
> VirtualHosts.
>
>>
>>
>> ServerAdmin admin@localhost
>> ServerName 168.127.1.19:8081
> This is, again, just a default value. It is in fact never used in this
> case.
>
>>
>> DocumentRoot "D:/docs"
>>
>> Options FollowSymLinks
>> AllowOverride None
>> Order deny,allow
>> Deny from all
>>
> Nitpick: the "Options FollowSymlinks" above does not seem to be useful,
> since you are forbidding access to "/" anyway (and rightly so).
>
>>
>> Options Indexes FollowSymLinks
>> AllowOverride None
>> Order allow,deny
>> Allow from all
>>
>>
>> DirectoryIndex index.html
>>
>>
> So it would seem that indeed you set the DirectoryIndex directive in the
> main configuration, and that it should thus be inherited by all
> VirtualHosts. Then why is it not working ? Mmmm.
>
> ...
>>
> I moved the section here at the end, because it seems more
> logical to first have all the default directives applying to all
> VirtualHosts, and then the definition of these VirtualHosts.
>
> >
> >
>
> So this is not a name-based VirtualHost system, it is an IP-based
> VirtualHost system, which is quite a different animal.
>
> > ServerAdmin admin@localhost
> > DocumentRoot "D:/docs"
> > ServerName 168.127.1.19:8081
> > ServerAlias 168.127.1.19:8081
> > # UseCanonicalName off
> > ErrorLog "logs/partners3/error.log"
> > CustomLog "logs/partners3/access.log" common
> > SetEnvIf Remote_Addr "168\.127\.1\.59" dontlog
> > RewriteEngine On
> > RewriteOptions Inherit
> > RewriteCond %{REQUEST_METHOD} ^TRACE
> > ReWriteRule .* - [F]
> >
> >
>
> The VirtualHost section does not redefine DirectoryIndex. The mystery
> gets thicker..
>
> But let's get back to your section
>
>
> In that section, you have a line
> SetHandler test
> (just like in other sections, you have a line
> SetHandler weblogic-handler
>
> Now THAT is the reason why your DirectoryIndex is not working !
> By this SetHandler directive, you are in fact telling Apache not to
> generate the content by itself, but to "delegate" (or proxy) this call
> to some add-on module. So Apache gives this request (any request for
> any URL starting with /tpg) to the "test" or to the "weblogic-handler"
> module, and expects this module to generate the response. And,
> presumably, these handlers have no idea that they should look for an
> "index.html" file in some directory.
> So they return whatever response they would return when give a URL of
> "/tpg" (probably, an error), and then Apache returns that response to
> the browser.
>
> It is only when Apache is asked to generate the content itself, with its
> own "default handler", that the DirectoryIndex directive will be
> invoked. In your case, Apache is not looking for anything, on disk or
> elsewhere. It is just passing the request to the module that you
> indicated as the handler.
>
> Do the following test :
> Add a new section as follows :
>
>
> SetHandler none
> DirectoryIndex index.html
>
>
> then make sure that you have a directory C:/Docs/tpg/indextest, and that
> it contains an "index.html" file.
> Then request http://hostname/tpg/indextest and see what happens.
>
>
> Because this is a sub-location of /tpg, and /tpg is defined to use the
> "test" handler (supposing it exists), we have to override this if we
> want Apache to use its normal own code to provide the response for a URL
> of /tpg/something.
> From there the "SetHandler none".
> See : http://httpd.apache.org/docs/2.2/mod/core.html#sethandler
>
> Also, it would have been impossible for anyone to find this out, if they
> did not see the full configuration above.
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
>

--
View this message in context: http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5826237.html
Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com.


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Issue with DirectoryIndex

In fact I pretty much went with defaults on where everything was located in
the configuration file. So, the VirtualHost information was where it was
located to begin with.

John


awarnier wrote:
>
> jwberger wrote:
>> I completely agree that it is most likely an issue with my config. I am
>> pretty new to Apache. Below is the complete config. I know I probably
>> did
>> not do some things correctly, but it is working good for except for this
>> one
>> thing that has just come up.
>
> No problem. This forum is the right place for that.
> As the final response will show, it just helps people here (for helping
> you) if you provide the full information from the start. Just 2 lines with
> Apache version : x.y.z
> platform : x.y v 0.3
> already narrow down the issue quite a bit.
> (And in this case, it would have helped a lot to mention that you are
> using Apache as a proxy to a WebLogic cluster; but let's not get ahead
> of ourselves).
>
> I am going to give you some personal comments below, which you might
> decide to use or not. Just based on personal experience.
>
>>
>>
>> ServerRoot "C:/Program Files/Apache Software Foundation/Apache2.2"
>>
> This is the standard installation path for the Apache/Windows MSI
> installer.
> It is OK, but I dislike it, because the path contains spaces, and spaces
> in paths will always bite you somewhere down the line.
> (E.g. when you call a script with another script and forget to quote
> things properly).
>
> In my opinion, the person who invented paths with spaces in them should
> get an Ig Nobel prize.
>
>>
>> Listen 168.127.1.19:8081
>>
> This could probably just be
> Listen 8081
>
> As you put it above it is valid, but it means that this Apache server
> will listen *only* on requests that come in on the interface that has
> that specific IP address. For example, it would not listen for requests
> on the "loopback" interface (127.0.0.1), and it would not listen anymore
> if ever you changed the IP address of the server.
>
>>
>> LoadModule actions_module modules/mod_actions.so
> ...
> OK
> ...
>>
>>
>> WebLogicCluster 168.127.136.85:9060
>> KeepAliveEnabled ON
>> KeepAliveSecs 30
>> FileCaching OFF
>>
>>
>>
>> SetHandler weblogic-handler
>> WebLogicCluster 168.127.136.85:9060
>>
>>
> The above and similar sections are not standard Apache stuff, and
> belongs to your WebLogic add-ons.
> This is intriguing. Where from did you get this Apache ?
>
>>
>
> AuthType basic
> AuthBasicProvider ldap
> AuthName "Partners"
> SetHandler test
> Order deny,allow
> Deny from all
> Allow from all
> # AuthLDAPURL ldap://boris.fnc.net.local:389/o=directory1.fnc.fujitsu.com
> AuthLDAPURL
> ldap://rchdmzldapd1.fnc.fujitsu.com:389/o=directory1.fnc.fuj itsu.com
> AuthzLDAPAuthoritative off
> Require valid-user
> >
>
> Ok, so far we are in what is called the "main configuration", meaning
> outside of any VirtualHost section.
> If you are using VirtualHost sections, then all this stuff in fact
> describes default values, that will be used by each VirtualHost later
> defined, unless that VirtualHost re-defines that particular parameter
> itself.
>
> Next, I have taken out your section, because where it was
> located in your configuration file, it was a bit confusing.
>
> All the following directives, being also outside of the
> section, are in fact member of the same group as the ones above. They
> belong to the main configuration, and also act as defaults for all
> VirtualHosts.
>
>>
>>
>> ServerAdmin admin@localhost
>> ServerName 168.127.1.19:8081
> This is, again, just a default value. It is in fact never used in this
> case.
>
>>
>> DocumentRoot "D:/docs"
>>
>> Options FollowSymLinks
>> AllowOverride None
>> Order deny,allow
>> Deny from all
>>
> Nitpick: the "Options FollowSymlinks" above does not seem to be useful,
> since you are forbidding access to "/" anyway (and rightly so).
>
>>
>> Options Indexes FollowSymLinks
>> AllowOverride None
>> Order allow,deny
>> Allow from all
>>
>>
>> DirectoryIndex index.html
>>
>>
> So it would seem that indeed you set the DirectoryIndex directive in the
> main configuration, and that it should thus be inherited by all
> VirtualHosts. Then why is it not working ? Mmmm.
>
> ...
>>
> I moved the section here at the end, because it seems more
> logical to first have all the default directives applying to all
> VirtualHosts, and then the definition of these VirtualHosts.
>
> >
> >
>
> So this is not a name-based VirtualHost system, it is an IP-based
> VirtualHost system, which is quite a different animal.
>
> > ServerAdmin admin@localhost
> > DocumentRoot "D:/docs"
> > ServerName 168.127.1.19:8081
> > ServerAlias 168.127.1.19:8081
> > # UseCanonicalName off
> > ErrorLog "logs/partners3/error.log"
> > CustomLog "logs/partners3/access.log" common
> > SetEnvIf Remote_Addr "168\.127\.1\.59" dontlog
> > RewriteEngine On
> > RewriteOptions Inherit
> > RewriteCond %{REQUEST_METHOD} ^TRACE
> > ReWriteRule .* - [F]
> >
> >
>
> The VirtualHost section does not redefine DirectoryIndex. The mystery
> gets thicker..
>
> But let's get back to your section
>
>
> In that section, you have a line
> SetHandler test
> (just like in other sections, you have a line
> SetHandler weblogic-handler
>
> Now THAT is the reason why your DirectoryIndex is not working !
> By this SetHandler directive, you are in fact telling Apache not to
> generate the content by itself, but to "delegate" (or proxy) this call
> to some add-on module. So Apache gives this request (any request for
> any URL starting with /tpg) to the "test" or to the "weblogic-handler"
> module, and expects this module to generate the response. And,
> presumably, these handlers have no idea that they should look for an
> "index.html" file in some directory.
> So they return whatever response they would return when give a URL of
> "/tpg" (probably, an error), and then Apache returns that response to
> the browser.
>
> It is only when Apache is asked to generate the content itself, with its
> own "default handler", that the DirectoryIndex directive will be
> invoked. In your case, Apache is not looking for anything, on disk or
> elsewhere. It is just passing the request to the module that you
> indicated as the handler.
>
> Do the following test :
> Add a new section as follows :
>
>
> SetHandler none
> DirectoryIndex index.html
>
>
> then make sure that you have a directory C:/Docs/tpg/indextest, and that
> it contains an "index.html" file.
> Then request http://hostname/tpg/indextest and see what happens.
>
>
> Because this is a sub-location of /tpg, and /tpg is defined to use the
> "test" handler (supposing it exists), we have to override this if we
> want Apache to use its normal own code to provide the response for a URL
> of /tpg/something.
> From there the "SetHandler none".
> See : http://httpd.apache.org/docs/2.2/mod/core.html#sethandler
>
> Also, it would have been impossible for anyone to find this out, if they
> did not see the full configuration above.
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
>

--
View this message in context: http://www.nabble.com/Issue-with-DirectoryIndex-tp25792416p2 5826287.html
Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com.


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Issue with DirectoryIndex

Hi John,
As there was so much to read through in the responses to
your question - If I missed this solve, I'm sorry..

> I am having an issue with the DirectoryIndex.

I had a similar problem recently. I had my DirectoryIndex
in the order I wanted in the conf file and it worked fine for
hundreds of years ;) until I upgraded to a newer distro.
I found I had to NOW add my unique DirectoryIndex order into
the 'dir.conf' in the /apache2/mods-enabled directory as a
instead of a

As you may be able to tell, I'm running on a Linux (UNIX clone)
server but I'm sure your wimpdows system uses the same filenames/DIRs

If your dir.conf file is empty, just enter the index files you
need (you may want to include all the index files you may use.
Notice, in my example, I have the .html last so the others are
looked for first.. I use perl a lot, so I have that first..

e.g.

DirectoryIndex index.pl index.php index.shtml index.html

Hope this helps in your case,
--
Nick. . .

_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/
. . . . . . . .
Soon to Launch: 99cHosting.com 50pHosting.co.uk and 75cHosting.eu
-=[ The prices are great - as is the service ]=-
. . . . . . . .
...---... (Stamp Out Spam and Save Our Servers) http://sosNow.ws
. . . . . . . .
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/

------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org